comment
authorJoey Hess <joeyh@joeyh.name>
Fri, 9 Sep 2022 16:30:46 +0000 (12:30 -0400)
committerJoey Hess <joeyh@joeyh.name>
Fri, 9 Sep 2022 16:30:46 +0000 (12:30 -0400)
doc/todo/not_ask_git_credentials_for_password_per_each_file/comment_1_ae15355f54b5137e696aaf5d2111806b._comment [new file with mode: 0644]

diff --git a/doc/todo/not_ask_git_credentials_for_password_per_each_file/comment_1_ae15355f54b5137e696aaf5d2111806b._comment b/doc/todo/not_ask_git_credentials_for_password_per_each_file/comment_1_ae15355f54b5137e696aaf5d2111806b._comment
new file mode 100644 (file)
index 0000000..5f2da4d
--- /dev/null
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2022-09-09T16:02:29Z"
+ content="""
+Is this a git-lfs special remote, or a git remote with an annex/objects
+directory? Probably does not matter, but also is unclear.
+
+`git credential` is doing the prompting here, and it supports caching, if
+you choose to enable that, by eg `git config credential.helper cache`.
+
+It feels redundant to add another layer of caching to git's existing cache.
+On the other hand, I suppose that `git pull` can make multiple http accesses
+and reuse the same credential for them, so that's kind of a precedent for
+caching during the lifetime of the process.
+"""]]